Update package.josn to match last seq release number #2674
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR does nothing but change the package.json version back to
17.2.0
so that the next release will be17.2.1
(which I will kickoff on merge). For some reason during the revert hub-bub, it made a release against17.1.3
. Talking with @chandlerprall and @thompsongl we decided just producing a new release back on cadence (and properly notied things in the CL) was the easiest course of action.Checklist
Checked in dark modeChecked in mobileChecked in IE11 and FirefoxProps have proper autodocsAdded documentation examplesAdded or updated jest testsChecked for breaking changes and labeled appropriatelyChecked for accessibility including keyboard-only and screenreader modes